From: D References: <7Zt5DHW8FTpPHEedl@bongo-ra.co> Subject: Fw: apparently comp.arch, comp.lang.c++, and com.lang.fortran are now read only at google groups Content-Transfer-Encoding: 7bit Message-ID: <9033af8a8cd4861f353e3d1e91bd3087@dizum.com> Date: Thu, 2 Nov 2023 01:34:14 +0100 (CET) Newsgroups: alt.comp.freeware Path: ...!news.mixmin.net!news2.arglkargh.de!sewer!news.dizum.net!not-for-mail Organization: dizum.com - The Internet Problem Provider X-Abuse: abuse@dizum.com Injection-Info: sewer.dizum.com - 2001::1/128 Bytes: 1637 Lines: 19 On 1 Nov 2023 21:51:38 -0000, kludge@panix.com (Scott Dorsey) wrote: >Mike Terry wrote: >>What will Google do assuming the spammers just move on to another group? They wouldn't want to make >>ALL their groups read only, and it can't be hard for the spammers to identify new target groups that >>haven't been locked down yet? > >That's basically the question. >And comp.os.vms is totally inundated now. >--scott message-id / reference headers including "googlegroups.com" . . . comp.os.vms =~ 5370 since 1 May 2023 (average, even below normal) p.s. seems the goo is doing a lot of newsgroup-shifting lately, reports of previously mass-googlespammed newsgroups seeing sudden steep declines, while other previously quiet newsgroups reporting sudden steep increases; could almighty google be spamming so much that it's running low on power?